Dynomotion

Group: DynoMotion Message: 9785 From: Sam Marrocco Date: 7/10/2014
Subject: Issue with Degrees property on an axis
GCode is running fine on all axes through DotNet and Interpret.Interpret() until I set the .Degrees property to true for a single axis (in this case, A). Moving the axis with .jog() seems to work, but simple gcode scripts stop working, such as:

G91
G0 A1

Is there something else that must be set to place the axis into "degrees mode"?

--

sam marrocco | chief technical officer
ringside.cutters.picnic.moonlink

248 548 2500 w
248 910 3344 c

ringsidecreative.com
Group: DynoMotion Message: 9786 From: Tom Kerekes Date: 7/10/2014
Subject: Re: Issue with Degrees property on an axis
Hi Sam,

You may need to set the RadiusA in degrees mode for the Trajectory Planner to determine the feed rate properly.  Either set it to a reasonable radius so the A motion can be included in the feedrate calculation properly or to zero for it to be excluded.  This Flash Video show it being used for KMotionCNC which uses the same underlying libraries.

http://dynomotion.com/Videos/BAxis9.swf.html

HTH
Regards
TK
From: "Sam Marrocco SMarrocco@... [DynoMotion]" <DynoMotion@yahoogroups.com>
To: DynoMotion@yahoogroups.com
Sent: Thursday, July 10, 2014 5:15 AM
Subject: [DynoMotion] Issue with Degrees property on an axis

 
GCode is running fine on all axes through DotNet and Interpret.Interpret() until I set the .Degrees property to true for a single axis (in this case, A). Moving the axis with .jog() seems to work, but simple gcode scripts stop working, such as:

G91
G0 A1

Is there something else that must be set to place the axis into "degrees mode"?

--

sam marrocco | chief technical officer
ringside.cutters.picnic.moonlink

248 548 2500 w
248 910 3344 c

ringsidecreative.com


Group: DynoMotion Message: 9787 From: Sam Marrocco Date: 7/11/2014
Subject: Re: Issue with Degrees property on an axis
On 7/10/2014 9:28 PM, Tom Kerekes tk@... [DynoMotion] wrote:
 
Hi Sam,

You may need to set the RadiusA in degrees mode for the Trajectory Planner to determine the feed rate properly.  Either set it to a reasonable radius so the A motion can be included in the feedrate calculation properly or to zero for it to be excluded.  This Flash Video show it being used for KMotionCNC which uses the same underlying libraries.

http://dynomotion.com/Videos/BAxis9.swf.html



That looks like it cured the issue. Thanks!




--

sam marrocco | chief technical officer
ringside.cutters.picnic.moonlink

248 548 2500 w
248 910 3344 c

ringsidecreative.com